Open topic with navigation

Work Item Release rollup iCube

The Work Item Release rollup iCube enables you to create ad hoc reports to help you in analyzing the number of work items committed for a release in comparison with the number of work items completed for that release.

Attributes

Expand this link to view the list of attributes available as part of the Work Item Release rollup iCube.

Attributes	Description
Work Item	Work Item refers to an issue that represents work to be completed. Work items can be of various types, such as task, enhancement, bug, epic, and so on
Work Item Fix Version	Release version in which the Work Item is expected to be fixed
Work Item Iteration	Iteration or Sprint to which the Work Item is associated. If a work item is associated with more than one iteration, only the latest iteration will be considered
Work Item Number	Unique identifier for the Work Item

Metrics

Expand this link to view the list of metrics available as part of the Work Item Release rollup iCube.

Metric Name	Description	Formula	Expected Value
% Spillover SP Release	Percentage of story points that have spilled over to the next release	([Committed Velocity Release] - [Completed Velocity Release]) / [Committed Velocity Release]	Closer to 0 i ideal
% WI Spillover Release	Percentage of work items that have spilled over to the next release	([Committed Count Release] - [Completed Count Release]) / [Committed Count Release]	Closer to 0 is ideal
Added Work Release	New Stories Added to the release divided by the Committed Velocity(SP)	[Stories Added Release] / [Committed Velocity Release]	>=0
Committed Count Release	Count of the work items committed at the beginning of the release	Sum([Committed Count Release])	>=0
Committed Hours Release	Planned estimate(current) at the beginning of an Iteration	Sum([Committed Hours Release])	>=0
Committed Tasks Release	Number of work items committed at the beginning of the iteration of type Task	Sum([Committed Tasks Release])	>=0
Committed Velocity Release	Planned story points at the beginning of release	Sum([Committed Velocity Release])	>=0
Completed Count Release	Count of work items completed at the end of the release	Sum([Completed Count Release])	>=0
Completed Tasks Release	Total Time Spent at the end of an Iteration during the Iteration	Sum([Completed Tasks Release])	>=0
Completed Velocity Release	Completed Story Points at the end of Iteration	Sum([Completed Velocity Release])	>=0
Defect Density Release	Number of defects fixed out of the total completed velocity	[Defects Fixed Release] / [Completed Velocity Release]	>=0
Defects Committed Release	Number of defects committed for work at the beginning of the release	Sum([Defects Committed Release])	>=0
Defects Fixed Release	Number of defects fixed in the release	Sum([Defects Fixed Release])	>=0
Defects Found Release	Number of defects found in the release	Sum([Defects Found Release])	>=0
Stories Added Release	Number of user stories added to the release	Sum([Stories Added Release])	>=0
Stories Committed Release	Number of user stories committed at the beginning of the release	Sum([Stories Committed Release])	>=0
Stories Completed Release	Number of user stories completed at the end of the release	Sum([Stories Completed Release])	>=0
Velocity Variation SP Release	Variation in the velocity of actual completed story points with respect to committed story points	([Completed Velocity Release] - [Committed Velocity Release]) * 100.0) / [Committed Velocity Release]	Closer to 0 is ideal